AltME groups: search

New r3-view.exe published. Fixes the problem, that the graphics subsystem 
wasn't initialized when command line arguments are given. So, now 
it behaves as before and should give correct STDIO.

Everything around it is done by Red, such as processing the command 
line arguments, opening and closing the database, injecting the SQL 
and processing status reports

thanks.  I didn't know Firefox took command line arguments

It's probably just me but what is the deal with command line arguments 
via system/script/args, I can't seem to get anything returned except 
none.

I finally got around to making a nice little "command line" function 
FIND-FILE.
You can use it with optional arguments like this:
	find-file *.r    ; just lists all files with ".r" suffix.

 find-file *.r "rebol"   ; lists all files with ".r" suffix and containing 
 "rebol" 
	find-file * "rebol"  ; all files containing "rebol"
etc...

yeah .. some of us are too old to remember command line arguments 
and tool usage

In windows, it starts up another instance with the values passed 
as command line arguments
eg, launch "test" where test is a command line argument

In Linux, it appears to treat "test" as a script which it can't find.

Ok, so here it is:

-fixed image keying bug (swapped color components in keying tuple!)
-line width is now now changing according to scale

-fixed rendering of transformed images(now uses aplha premultiplied 
data)

-fixed LINE-PATTERN bug (multiple line patterns in DRAW block should 
work properly now)

-fixed MATRIX bug(wrong matrix calcualtion was corrected in this 
case)

-fixed SKEW command inconsistency (now it takes degrees as arguments 
instead of radians)

-fixed FILL-PEN bug when filling images (now it doesn't render images 
upside down)

-fixed ANTI-ALIAS cmd(now it is possible to switch this mode within 
one DRAW block)

-removed POP command (was obsolete, PUSH with block! arg is used 
instead)
-fixed fill/outline pixel aligning problem
-fixed visual bug when rendering circle with line-width > 1
-fixed text character encoding problem
-improved gradients: added REFLECT and REPEAT modes, example:
view layout [
	origin 0
	box 400x460 effect [
		draw [
			pen none
			fill-pen linear 10x10 0 190 0 1 1 black red green blue black
			box 10x10 390x90

   fill-pen linear 10x160 0 190 0 1 1 black red green blue black repeat
			box 10x100 390x180

   fill-pen linear 10x310 0 190 0 1 1 black red green blue black reflect
			box 10x190 390x270
			fill-pen radial 80x350 0 20 0 1 1 black red green blue black
			circle 80x350 70

   fill-pen radial 190x350 0 20 0 1 1 black red green blue black repeat
			circle 190x350 70

   fill-pen radial 320x350 0 20 0 1 1 black red green blue black reflect
			circle 320x350 70
		]
	]
]

I added a few new things to the BASIC:

added DELETE command, added arguments to LIST, added STOP statement 
and some more (see source). Example of use:

>> do http://www.fys.ku.dk/~niclasen/rebol/basic.r
connecting to: www.fys.ku.dk
Script: "BASIC" (24-Jun-2007)
BASIC

>auto 5 5
    5 print "Line 5"
   10 rem goto 20
   15 blab
   20 print "Line 20"
   25 stop
   30 0
>run
Line 5

Mistake at line 15
>10 goto 20
>run
Line 5
Line 20

STOP at line 25
>

At last, the electronic pre-release of Chapter 6 of the translation 
of Olivier Auverlot's "Rebol - Guide du Programmer" (http://www.rebol.com/article/0324.html) 
is now available atÊ(Êhttp://www.lulu.com/content/4426599Ê) for EUR 
2.99.

This chapter starts with a short overview of how to configure 
and manage Rebol/View desktops to provide a "virtual office". It 
moves quickly into serious programming topics in a Unix environment 
covering console data display, handling keystrokes, command line 
arguments, file access rights, shell access, pipes, sockets, Unix 
signals and dynamic library calls. A thorough introduction to RebDB 
rounds out the chapter.

args.r  released on rebol.org...  pretty powerfull command-line argument 
management. 

*dialect driven
*typed arguments.  
*optional arg support (with default values)
*different flag modes
*automatic command-line error reporting
*and much more...


the idea is not to provide a rebol interface to the cli, but provide 
a cli interface to rebol.   so for example, to escape chars, we use 
"\"  not "^" .

the systems builds a parse rule out of your command-line spec and 
runs it against the  supplied string.


there is a preliminary demo which shows how to use it... full docs 
expected this week-end.  (they are drafted, but need to be revised 
and organised properly).

Is it possible to send command -line arguments to the new REBOL process 
using LAUNCH?
launch "test.r" ;this one works

launch "-s test.r" ;REBOL starts in TRACE ON mode (I don't know if 
%test.r will start or not, too much trace log to wait)

launch "--secure allow test.r" ;shows USAGE and doesn't start %test.r
launch "-q test.r" ; trace mode again.

<PARAM NAME="Args" VALUE="?"> ? Command-line arguments passed to 
the script (available in system/options/args).

Maxim, see this about passing arguments to apps started by file association:


http://stackoverflow.com/questions/444388/how-can-i-pass-command-line-arguments-via-file-association-in-vista-64


Re. shortcuts having arguments, yes they can - Vista shortcuts could 
as well, though.

and yes... you have to manually change the command-line arguments, 
but then the OS' editors break up in what I can't remember, I think 
rebol disapeared from the "installed applications" list, although 
the file association still worked.

I'd like to know if any of you want to be alpha testers for the up 
and comming version, which is a result of several YEARS of fine tuning, 
 and now combining, a rich set tools.

CURRENT FEATURES (partial list):
General:
-----------------------
-non intrusive, does not force any programing onto you.

    ex:  * no need to have version in header, and can still do version 
    control

           * history format is user specified, massive configurability
-encapped (windows) application, so its easy to use.

-no external dependencies (ex: zip archive is embeded, and coded 
in rebol :-)


Automated:
-----------------------
-script versioning
-file backup (versioned)
-zip archival
-file management

-creation of "packages" (create dirs, copy files, archive, prebol, 
slim-link, encap, etc)

-header manipulation (including history, date, version, and any field 
you want to enforce)
-system calls
-file parsing, replacing info tags.

Flexible setup:
-------------------------
-cascading configuration (global, user, project, + per file)

-config locking, prevents overiding configs in cascaded setups (project 
manager can create rules which no one can break)
-command-line arguments overides for many configs

-user set configs for most if not all features (ex: history format, 
date format).

and much more

Lit-word arguments are for functions that treat words as keywords 
or part of the syntax, or for interactive command line functions 
that are supposed to act like shell funcs. If you use lit-word arguments, 
you can't easily generate the value passed using an expression, especially 
in R2 - in R3, those expressions can be put in parens, as is emulated 
in the R2 mezzanine backports of R3 functions that take lit-word 
arguments. For instance, if you made GET take a lit-word argument, 
GET IN wouldn't work.

Command line arguments access now available: http://groups.google.com/group/red-lang/browse_thread/thread/4b8cb7a5a49308ba?hl=en